Method and system for facilitating data access and management on a secure token

ABSTRACT

A system for facilitating data access and management on a smart card is provided. According to one exemplary aspect of the system, a storage architecture is provided in the smart card which allows data stored thereon to be shared by multiple parties. Access to data stored on the smart card is controlled by various access methods depending on the actions to be taken with respect to the data to be accessed.

CROSS-REFERENCES TO RELATED APPLICATION(S)

[0001] The present application claims the benefit of priority under 35 U.S.C. § 119 from U.S. Provisional Patent Application Serial No. 60/416937, entitled “METHOD AND SYSTEM FOR FACILITATING DATA ACCESS AND MANAGEMENT ON A SMARTCARD”, filed on Oct. 7, 2002, the disclosure of which is hereby incorporated by reference in its entirety for all purposes.

BACKGROUND OF THE INVENTION

[0002] The present invention generally relates to data access and management and, more specifically, to a method and system for facilitating data access and management on a secure token, such as, a chip card or smart card.

[0003] Current technologies now allow multiple applications to be implemented on a single chip card. This ability to have multiple applications on a chip card has been identified as one of the key components for enhancing the business case of a chip card program. These multiple applications include, for example, value-add programs and the associated data required to operate them successfully. From a business perspective, it is preferable that value be obtained for all parties involved in the chip card program, including the issuer, acquirer, application owner, value add service provider and the cardholder.

[0004] Critical to the success of value-add applications on the chip card is the ability to maximize and efficiently use available space on the chip card to allow multiple applications or programs to operate, and to deploy an acceptance infrastructure that allows consumers to take full advantage of the functionality provided by the chip card.

[0005] While it is now possible to implement multiple applications on a chip card, these multiple applications (and their associated data) are often kept independent of one another within the chip card. For example, data belonging to one application is not shared by another application within the chip card, which in some cases result in redundancy. Due to the limited size of the chip card, such redundancy adversely affects the optimal use of resources on the chip card.

[0006] Hence, it would be desirable to provide a method and system that is capable of facilitating data access and management on a chip card in a more efficient manner.

BRIEF SUMMARY OF THE INVENTION

[0007] A method and system for facilitating data access and management on a smart card is provided. According to one exemplary embodiment, the smart card includes a storage architecture that allows data stored thereon to be shared by multiple parties. Access to data stored on the smart card is controlled by various access methods depending on the actions to be taken with respect to the data to be accessed.

[0008] According to one exemplary embodiment, the storage architecture provides a file structure that can have separate instances of the file structure. A separate instance is referred to as an environment. In one instance, an environment includes the common commands applet providing access to a directory, one or more cell groups under the directory (with each cell group being a sub-directory), and one or more cells under each cell group. Attributes and access conditions can be set at different levels including, for example, at the directory level, the cell group (or sub-directory) level and the cell level. This allows varying access levels for different parties thereby permitting data to be shared in various manners.

[0009] According to one exemplary embodiment, the storage architecture is implemented on a GlobalPlatform smart card. GlobalPlatform is an international smart card consortium of companies in the smart card industry which creates and advances standards and/or specification for smart card infrastructure. Alternatively, the storage architecture can also be implemented on a static or native smart card, i.e., a smart card having its own proprietary operating system.

[0010] Reference to the remaining portions of the specification, including the drawings and claims, will realize other features and advantages of the present invention. Further features and advantages of the present invention, as well as the structure and operation of various embodiments of the present invention, are described in detail below with respect to accompanying drawings, like reference numbers indicate identical or functionally similar elements.

BRIEF DESCRIPTION OF THE DRAWINGS

[0011]FIG. 1 is a simplified schematic diagram illustrating one exemplary embodiment of the present invention;

[0012]FIG. 2 is a simplified schematic diagram illustrating an exemplary file structure according to one exemplary embodiment of the present invention;

[0013]FIG. 3 is a table illustrating an exemplary embodiment of the XCID according to one exemplary embodiment of the present invention; and

[0014]FIG. 4 is an exemplary embodiment of a table of contents according to the present invention.

DETAILED DESCRIPTION OF THE INVENTION

[0015] The present invention in the form of one or more exemplary embodiments will now be described. Generally, the present invention is used to access and update data on a secure token, such as, a chip card or smart card. According to an exemplary embodiment, an open storage architecture is provided for applications on a secure token, such as, a chip card or smart card. This architecture can be used to access and store both static and dynamic data elements on smart cards for use by value-added applications.

Architecture Overview

[0016]FIG. 1 is a simplified schematic diagram illustrating an exemplary embodiment of the present invention. In one exemplary embodiment, a system 100 includes a client 102 and a smart card 104. The client 102 includes one or more applications 106. The client 102 communicates with the smart card 104 using application protocol data units (APDUs). The smart card 104 is prepared by an issuer 116 in a personalization process. The client 102 also communicates with one or more backend systems operated by a value add service provider 114 in cooperation with the corresponding applications 106.

[0017] The smart card 104 includes a set of environments—a set of common commands applet 108, and a storage architecture named “Smart Storage” 112. The set of common commands 108 is used to facilitate interactions between the applications 106 and their corresponding application storage 110 within Smart Storage 112 on the smart card 104. A person of ordinary skill in the art should appreciate how to implement the set of common commands 108. In an exemplary embodiment, the set of common commands is installed onto the smart card 104 having a specific application storage 110 linked to a corresponding client application 106. As will be further described below, the Smart Storage 112 allows a file structure to be created once thereby providing specific files for each corresponding client application 106. Depending on how the file structure is created, the file structure may allow data to be shared by other client applications 106.

[0018] As will be further described below, the present invention allows an issuer of the smart card 104 to prepare space on the smart card 104 for a future implementation of applications or services. This space can be pre-allocated at personalization time (i.e., when the smart card 104 and environment is personalized); alternatively, the issuer can designate use of the space and to whom the space will be allocated after the smart card 104 has been personalized and issued. At the time of personalization of the smart card 104, the issuer does not need to have actual knowledge of the size or content of the data that will be stored in individual files on the smart card 104.

[0019] Once the smart card 104 is personalized, the issuer can decide later how to allocate and authorize use of the space on the smart card 104. In addition to defining the size of storage space, the issuer also defines the access and authorization methods necessary to enable access to the storage space. The storage architecture 112 allows an organization of the storage space into groups—application storage 110, which can then be allocated to various business partners, e.g., program operators. Access to specific portions of these groups can then be defined by the program operators in more detail.

[0020] In an exemplary embodiment, the storage architecture 112 is an organization of data that can be retrieved and updated using a common commands applet. FIG. 2 illustrates an exemplary file structure of the storage architecture 112. The file structure 200 includes a master file 202 and one or more directories 204 identified by corresponding application identifiers (AIDs). Each directory 204 can be viewed as a storage instance of the storage architecture 112. For each directory 204, there is a number of associated files containing information that is used to facilitate communications between the common command applet and corresponding application. For example, such associated files include an application identification file, a status file, a key file, a security environment file, a certificate file, a passcode file and a reset passcode file, etc. One or more of these files are used to ensure that the common command applet is able to communicate with the corresponding directory 204 and files thereunder.

[0021] The application identification file contains a unique number to identify each storage instance contained on the smart card 104, plus related application information on that specific smart card, including, for example, a version number. Preferably, the issuer is responsible for creating both this unique number and additional data during personalization.

[0022] The status file contains specific status information (e.g., status of the smart card, customer segment or expiration date, etc.).

[0023] The key files contain cryptographic keys that are used for signatures and key/passcode encryption purposes.

[0024] The security environment file contains the access conditions for a specific cell group.

[0025] The certificate file contains RSA certificates.

[0026] The passcode file is used to store a cardholder passcode.

[0027] The reset passcode file is used to store special reset-codes, which is used in an off-line environment to reset the cardholder's passcode.

[0028] In one exemplary embodiment, each directory 204 further includes one or more cell groups 206. Each cell group 206 can be viewed as a sub-directory. Each sub-directory 206 can represent storage space for a corresponding application. These cell groups 206 are created at the time the smart card 104 is personalized or issued. The number of cell groups 206 that can be created depends on, amongst other things, the issuer of the smart card 104. For example, an issuer may want to reserve a specific amount of space for future utilization for a certain application. In some situations, the owner of specific cell groups is not known at the time of the smart card personalization. In such cases, ownership of cell groups can be transferred after the smart card 14 has been issued. Optionally, subject to space availability on the smart card 104, additional cell groups 206 can be created after the smart card 104 has been issued, for example, to a cardholder. Typically, creation of additional cell groups 206 is controlled by the issuer of the smart card 104. For each cell group, a maximum number of bytes and a maximum number of cells beneath that cell group are defined—thus giving the issuer the ability to control how much space is allocated for each application storage 110. In the context of the ISO 7816-4 standard, a cell group is contained in a dedicated file (DF). In an alternative exemplary embodiment, a directory 204 may not include any cell groups 206. Instead, cells can be created directly under an AID that has no cell groups. Description relating to cells will be further provided below.

[0029] For each cell group 206, there may be associated security attributes, such as keys, that are used to access that cell group 206. These security attributes are initially set by the issuer of the smart card 104 and then subsequently provided to the program operator. The value add service provider can then use these security attributes to access the cell group 206. Optionally, the security environment associated with a cell group 206 can be modified, thereby preventing a previously approved value add service provider from accessing that cell group 206 and/or allowing a new value add service provider to access the same.

[0030] Each cell group 206 is made up of one or more cells 208. Cells 208 are the actual storage entities within the storage architecture 112. In an exemplary embodiment, each cell 208 includes cell attributes, access conditions and data. Alternatively, within the storage architecture 112 or application storage 110, each part of the space that is separated from the other parts by a specific defined access-method, by a specific access-condition or simply by a logical separation, is called a cell 208. The management of each cell 208 is dependent on the corresponding access conditions for that cell in a specific implementation. In an exemplary embodiment of a file system using the ISO 7816-4 standard, a cell is contained in an elementary file (EF). Typically, data contained in a cell is program-specific data. Cell data can be managed by a back-end host system such as a loyalty host system, customer relationship management (CRM), customer database or a consumer-driven client application.

[0031] A number of cells are maintained within the storage architecture 112 or application storage 110. If neither the owner nor the content of specific cells is known at the time of the smart card personalization, the personalization process only defines the common commands applet and, if the issuer chooses, a number of pre-defined cell groups with default access conditions. Cells within a pre-defined cell group can then be created after the smart card 104 has been issued. In other words, the number of cells and the size of each cell do not have to be specified before personalization of the smart card 104. Preferably, however, a preliminary sizing assessment should be made to ensure maximum utilization of the available card storage capacity.

[0032] Furthermore, it should be noted that a cell is what makes a corresponding file identifiable to the external world, such as, the client 102. Via the use of a cell, data from a corresponding file on the smart card 104 can be accessed and manipulated by a client 102 without requiring the client 102 to know the underlying details and logistics concerning the actual address of the data on the smart card 104.

[0033] As mentioned above, cells can be organized within a sub-directory called a cell group. The keys used for controlling access to cells under a cell group are defined at the cell group level.

[0034] Within the Smart Storage 112, security attributes are assigned to files on two levels, namely, a cell group file and a cell file. The security attributes for cell group files and cell files can be assigned during smart card personalization.

[0035] The cell group file contains security attributes which define the conditions for creating and deleting a file within that cell group. Authority to create files can be limited to the value add service provider having access to the keys for a specific cell group. Likewise, the conditions for creating and deleting the files directly under a directory 204 AID can be limited to a single entity, for example, the issuer.

[0036] The cell file is assigned security attributes which define when a client 102 can create, read, update or delete data from the cell or whether data is to be encrypted during transport to or from the cell.

[0037] In order to be able to recognize each cell, the common commands applet maintains a table of contents of all cells within the corresponding storage instance. This table of contents is linked to the specific AID associated with the corresponding storage instance implemented logically on a cell group level. Hence, for a specific AID or storage instance, a table of contents is maintained for all active cells (i.e., cells containing data) grouped into specific cell groups. The table of contents is used by the client 102 to address a specific cell in the corresponding storage instance or application storage 110. There can be multiple storage instances on the smart card 104, but each storage instance has its separate table of contents administered by the corresponding common commands applet.

[0038] The common commands applet has no knowledge of the actual contents of a cell. The common commands applet only administers access to a cell. It is up to the client application 106 to interpret the contents of a cell. Furthermore, the client application 106 is equipped with information on the requisite keys and software that apply to a specific cell and the respective access conditions for specific cells. In some situation, clients 102 may be able to get on-line access to an issuer or value add service provider back-end system in order to retrieve the information necessary to access specific cells.

[0039] As mentioned above, each cell may be associated with an access method or access conditions. Optionally, no access method may be defined for a specific cell, meaning that the cell can be freely accessed. In one exemplary embodiment, one of a number of access methods can be associated with a cell. Such access methods can be categorized based on different domains including, for example, cardholder domain, card issuer domain and value add service provider domain. In the cardholder domain, a cardholder wishing to access a cell is prompted to provide a passcode in either clear or encrypted text. In the card issuer domain and the value add service provider domain, a digital signature is provided in order to gain access to the cell.

[0040] Also, as mentioned above, each cell includes attributes that are unique to that cell and its contents. These attributes are applied by the owner of the contents contained in the cell and may vary during the different stages of smart card life cycle and usage. These stages include, for example, initialization where the issuer is responsible for protecting the cells from unauthorized access prior to card personalization; personalization where the issuer may transfer responsibility and authority for the cell and its contents based upon a pre-established agreement with the entity performing personalization; activation where unique attributes may be added to the cell by the value add service provider or the cardholder; usage where data may be modified during cardholder usage to reflect specific program data usage; and deactivation where data may be deactivated or deleted to reflect that the content has been used or expired or that the data is no longer of interest to the cardholder.

Cell Management

[0041] AIDs on the smart card 104 are assigned by an issuer of that smart card 104. In one implementation, a credit card service association, such as Visa, provides unique AIDs to issuers for interoperability reasons. Furthermore, under each AID, the issuer determines which value add service provider(s) are eligible to access and manage data under that specific AID. Each value add service provider is identified by an unique identifier or value add service provider ID. The cell ID (CID) is an identifier assigned by the value add service provider. The CID is unique within a given value add service provider ID. If multiple value add service providers are using the same storage architecture 112, each such value add service provider is identified by its own corresponding value add service provider ID. The unique CID can therefore be a combined element, as further described below. This unique CID for multiple program operators is referred to as extended CID or XCID. FIG. 3 is a table illustrating an exemplary embodiment of the XCID.

[0042] Each cell contains data related to a specific program, scheme, implementation or application and is uniquely identified within the storage architecture 112. In order to uniquely identify a cell, a unique global identifier is defined. In one exemplary implementation, in order to create unique CIDs, each value add service provider applies to ISO (International Standards Organization) for a unique registered application provider identifier (RID) before they are able to implement the present invention. Each value add service provider can then use its unique RID to create its own CIDs. Typically, value add service providers are responsible for ensuring the uniqueness of all CIDs assigned under their AIDs.

[0043] It should be understood that within a specific CID, a further detailed breakdown of the cell content into specific programs is possible. In an exemplary implementation, it is up to the value add service provider to implement a detailed layout of programs including, for example, a further detailed “table of contents” of the cell.

[0044] A cell locator is used to locate a cell. The cell locator is the logical address of the specific file containing the cell within the smart card 104. It is stored in the table of contents maintained by the common commands applet and is used to locate a specific cell based upon a request from the client application. In one exemplary implementation, the cell locator is the cell file ID under the cell group in which the cell resides.

[0045] As mentioned above, the common commands applet contains a corresponding table of contents with information on the location of specific cells. The table of contents translates the external ID for a specific cell (i.e., the XCID) to the internal actual physical file on the smart card 104 that contains the data for that cell. Hence, the table of contents is a composite element combining the XCIDs and the cell file IDs for a specific cell group. A unique table of contents is created for each application storage 110 created under the storage architecture 112. FIG. 4 illustrates an exemplary table of contents.

Security Attributes

[0046] As mentioned above, security attributes can be assigned to a directory 204, a cell group 206 and a cell 208. In one exemplary implementation, the security attributes provided under the storage architecture 112 are based on the security attributes as defined in ISO 7816-9 and the security environment as defined in ISO 7816-8. A person of ordinary skill in the art will appreciate how to use the ISO standards to provide the security attributes according to the present invention. For purposes of definition, some of the names in parentheses below are taken from the ISO standards.

[0047] Permissions (Access Modes)

[0048] In an exemplary implementation, permissions (Access Modes) are defined for cells and cell groups or AIDs. With respect to permissions for cells, such permissions are defined on a cell level as Access Mode bytes for EF's. The permissions allow or restrict the following functions or operations to take place: (1) create cell (creates a cell within the storage architecture 112, inserts the CID into the table of content and creates the Cell-attributes); (2) read cell data (returns data in a cell to the client application); (3) update cell data (updates the data in a cell); and (4) delete cell (blanks out the data in a cell, blanks the cell attributes and deletes the CID in the table of contents).

[0049] With respect to permissions for cell groups or AIDs, such permissions are defined on a cell group level or AID level as Access Mode bytes for DF's. The permissions allow or restrict the following functions or operations to take place: (1) create file (creates the DF file containing the cell group or the EF file containing the cell and the security attributes of the cell group or cell); and (2) delete file (deletes the DF file containing the cell group or the EF file containing the cell). These permissions allow creation or deletion of a file under a specific cell group or AID. This means that the permission to create and delete a DF file is made on the AID level, while the permission to create and delete an EF file is made for a specific cell group.

[0050] Access Methods

[0051] Access to data contained in a cell is based on a matrix including possible methods and supported functions. In an exemplary implementation, there are six permission or access methods including, for example, (1) signature inbound (SM command)—either a message authentication code (MAC) created using a triple DES symmetric cryptographic algorithm (TDEA) session-key, or an RSA-based digital signature; (2) signature outbound (SM response)—either a MAC created using a TDEA session-key, or an RSA-based digital signature; (3) encrypted passcode (user authentication, knowledge-based)—either an ISO 9796-1 format 1 encrypted Passcode using a TDEA session key, or a PKCS #1 RSA-OAEP formatted passcode wrapped in a RSA public key; (4) clear passcode (user authentication, knowledge-based)—a passcode presented in clear text; (5) key exchange-encrypted (encipherment/decipherment)—key is encrypted before being returned or decrypted before being received; and biometrics (user authentication, biometric-based).

[0052] Interactions Between Permissions and Methods

[0053] For each of the six functions mentioned above in connection with permissions for cells and cell groups or AIDs, one or more of the six access methods can be set. The access method(s) for one function can be set independently from another function.

[0054] The three methods, signature inbound (SM Command (CCT, DST)), encrypted passcode (user authentication, knowledge-based (AT)), and clear passcode (user authentication, knowledge-based (AT)), are access conditions to be met before the common commands applet will perform the specific function. The access conditions can be met as part of the transaction (signature inbound) or can be satisfied in a previous command to the common commands applet. (encrypted passcode or clear passcode).

[0055] The method, signature outbound (SM Response (CCT, DST), causes the common commands applet to perform a signature generation on both the data in the command to which it responds and on the data in the cell.

[0056] The method, cell-data exchange encrypted (Encipherment (CT) for read and Decipherment (CT) for update), causes a key to be decrypted before the data is updated (for the update functions) or encrypted before the key is returned via the read function.

[0057] The two methods, encrypted passcode and clear passcode, are mutually exclusive.

[0058] Rules for Security Environment

[0059] In on exemplary embodiment, the implementation of the permissions and their associated access methods is based on the security environment (SE) as defined in the ISO 7816-8 standard. Since the storage architecture 112 allows creation of files containing SE's and files containing keys under a cell group after personalization, there are some additional implementation-specific rules for these files. For example, if a SE file for a specific cell group is not present, the SE file for the AID is used instead; if a specific SE number is not present in a SE file for a specific cell group, the same SE number in the SE file for the AID is used, if available; if a key file for a specific cell group is not present, the key file for the AID is used instead, even if the key is referenced via a SE file for the cell group; if a specific key index is not present in a key file for a specific cell group, the same key index in the key file for the AID is used, if available; and the SE file for the AID is not updated.

Authentication Methods

[0060] For the purpose of authentication after personalization, the storage architecture 112 supports a number of authentication methods including, for example, TDEA-signatures or MAC, RSA-signatures or digital signatures, encrypted passcode and clear passcode. A person of ordinary skill in the art will appreciate how to incorporate various authentication methods for use in connection with the present invention.

Permissions for Creating Cells

[0061] In one exemplary implementation, creation of cells is controlled by the issuer of the smart card 104. The issuer can delegate authorization for creating cells under a specific cell group to a value add service provider after the a smart card has been personalized, thus transferring ownership of such cell group to the value add service provider.

[0062] Ownership

[0063] The owner of the cells is the entity holding the key allowing creation and deletion of cells in a specific cell group or AID. Initially, the owner is the issuer of the smart card who personalizes the initial keys into the key files, but the issuer can delegate ownership to a specific value add service provider in a number of ways. For example, in an on-line environment, ownership can be transferred by establishing a secure messaging transaction between the issuer and the smart card by using an on-line connection between the value add service provider and the issuer; alternatively, in an off-line environment, by distributing the keys for a specific cell group to the value add service provider before the smart card is introduced into the value add service provider's system.

[0064] Methods for Creating Cells

[0065] It is possible to define an open access control for creating cells, i.e., any entity can create cells on the smart card 104. In an exemplary embodiment, one entity, such as an issuer, controls the use of space on the smart card 104. In that situation, a number of different methods can be used to obtain permission to create cells including, for example, use of a RSA-signature (which requires an issuer public key on the smart card) or a TDEA-signature (which requires a derived secret key on the smart card).

[0066] Update of Key File

[0067] An update of the key file can reflect that a specific value add service provider or merchant now has ownership of a cell. This can occur as a normal update record command with a special set of security attributes allowing encryption of the key during transport. A number of encryption methods including, for example, RSA-encryption and TDEA encryption, can be used to encrypt the keys to be updated in the key files.

Keys

[0068] The storage architecture or Smart Storage 112 is very flexible as to which keys are used to access files and how they are used. Keys are stored in key files with an attached key index referenced internally from the various files to be protected. This means for instance that the same file can be protected by different keys that relate to different commands (e.g. one key for read, another key for update) or that multiple files can be protected by the same key for all commands.

[0069] In an exemplary embodiment, two sets of keys are used. One set is used for transferring ownership of card-space from the issuer or its delegate to the value add service provider or its delegate. In an exemplary implementation, the set of keys used in the transfer of ownership is installed when the smart card is personalized.

[0070] Another set is used by the value add service provider to access specific cells. Generally, this set of keys can be installed after a smart card is issued. These keys control access to cells and authentication of specific cell data. They are typically installed at the time of transferring ownership for a given cell from the issuer to the value add service provider. Once transferred, these keys are the responsibility of the value add service provider.

Storage Architecture Attributes

[0071] For each of the storage architecture or Smart Storage elements: cell, cell group and AID, a number of attributes are attached. Based on the disclosure and teachings provided herein, a person of ordinary skill in the art will appreciate other attributes that can be used in connection with the present invention.

[0072] Cell attributes

[0073] Cell attributes are set during creation of a cell, either during card personalization or via a Create Cell command. The cell attributes can also be changed using an Update Cell-status command. In one exemplary embodiment, the Create Cell and Update Cell-status commands are part of the set of common commands described above. These attributes include, for example, cell status, cell activation date, cell expiry date and cell log file ID, as will be further described.

[0074] Cell status is a status-byte for the cell providing information on whether the content of the cell is available or not. In one exemplary embodiment, the possible status-codes are: (1) Active (cell content is available with no restriction); (2) Opt-out (even though the cell exists, the cardholder has chosen not to make use of the content); and (3) Used (even though the cell exists, the cardholder has already made use of the content of the cell or, even if the cell expiry date has not been reached, the content of the cell is consider expired).

[0075] The cell activation date is used to identify the date from which the content of the cell can be read or updated. A cell is not considered available unless the Cell activation date has been reached and should not be read or updated before that date. If the cell activation date for a specific cell is not present, the cell is considered available by default.

[0076] The cell expiry date is used to specify when the content of the cell can no longer be used. A cell is not considered available if the cell expiry date has been reached and should not be read or updated after that date. If cell expiry date for a specific cell is not present, the cell is considered available by default.

[0077] The cell log file ID is used to identity the file in which logging of update, create and delete commands of a cell is stored.

[0078] Cell group attributes

[0079] In one exemplary embodiment, there is a number of cell group attributes including, for example, cell group status. Cell group status can be set during creation of a status file for a cell group either during personalization or by updating the status file for the cell group. The cell group status can assume one of a number of status codes including, for example, (1) Active (cell content is available with no restriction); (2) Opt-out (cardholder has chosen not to make use of the cells under the specific cell-group); (3) Inactive (cell group is present but not yet active); and (4) Blocked (cell group is not to be used). Typically, it is up to the client to define what action will be taken on receipt of the status codes.

[0080] AID attributes

[0081] In one exemplary embodiment, there is a number of AID attributes including, for example, AID status and AID expiry date. The AID status is set during the creation of a status file for an AID either during personalization or by updating the status file for the AID. The AID expiry date is used to identify when a specific instance of the applet or the application is considered expired and can no longer be used.

[0082] As described above, the present invention provides a set of functions and a repository for data that allow multiple parties with existing business relationships to access and share chip card data according to agreed security controls.

[0083] In an illustrative application, the sharing of information may be between an airline and a grocery store. The chip card incorporating the present invention can contain the consumer grocery store program number and the airline frequent flier number used by existing back end host systems. In order to facilitate the identification of the consumer and validate participation in a joint promotional program, the grocery store is given access to both the airline frequent flier number and the grocery store program number stored in the chip card. However, if the consumer is not participating in the joint promotional program, then the airline program is denied access to the grocery store program number on the chip card.

[0084] In another illustrative application, the present invention allows sharing of information between multiple parties including, for example, an issuer, a merchant and a third-party sponsor such as a credit card service association. The issuer, the merchant and the third-party sponsor may be involved in a joint loyalty program. Each of these parties may store its information on a smart card issued to a cardholder. The information stored by these parties on the smart card can be shared in a number of ways. In one instance, the issuer may allow both the merchant and the third party sponsor to access one portion of its information stored on the smart card; in another instance, the issuer may allow only the third party sponsor to access another portion of its information while denying access to the merchant. Furthermore, access to the information can be controlled based on different access methods depending on actions to be taken with respect to the information to be accessed. Based on the disclosure and teachings provided herein, a person of ordinary skill in the art will know of other ways and/or methods to deploy the present invention in various applications.

[0085] According to one exemplary embodiment, the storage architecture or Smart Storage is implemented on a GlobalPlatform smart card. Alternatively, the storage architecture can also be implemented on a static or native smart card, i.e., a smart card having its own proprietary operating system.

[0086] It should be understood that the present invention can be implemented using control logic, in the form of software or hardware or a combination of both. Based on the disclosure and teachings provided herein, a person of ordinary skill in the art will appreciate other ways and/or methods to implement the present invention.

[0087] It is understood that the examples and embodiments described herein are for illustrative purposes only and that various modifications or changes in light thereof will be suggested to persons skilled in the art and are to be included within the spirit and purview of this application and scope of the appended claims. All publications, patents, and patent applications cited herein are hereby incorporated by reference for all purposes in their entirety. 

What is claimed is:
 1. A system for facilitating data management on a secure token, comprising: a client having a plurality of applications residing thereon; and a secure token having a storage architecture, wherein the storage architecture includes: a directory and one or more attributes associated with the directory, wherein the one or more attributes associated with the directory are used to control access to the directory by the plurality of applications, one or more cell groups under the directory, each cell group having one or more associated attributes, wherein the one or more attributes associated with a cell group are used to control access to that cell group by the plurality of applications, and one or more cells under each cell group, each cell having one or more associated attributes, wherein the one or more attributes associated with a cell are used to control access to that cell by the plurality of applications.
 2. The system of claim 1 wherein the one or more attributes associated with the directory permit access to the directory by one application and deny access to the directory to another application.
 3. The system of claim 1 wherein the one or more attributes associated with the cell group permit access to that cell group by one application and deny access to that cell group to another application.
 4. The system of claim 1 wherein the one or more attributes associated with the cell permit access to that cell by one application and deny access to that cell to another application.
 5. The system of claim 1 wherein one or more additional cell groups are added to the directory subsequent to issuance of the secure token to a token holder.
 6. The system of claim 1 wherein ownership of one of the one or more cell groups is determined subsequent to issuance of the secure token to a token holder.
 7. The system of claim 1 wherein ownership of one of the one or more cell groups is modified subsequent to issuance of the secure token to a token holder.
 8. The system of claim 1 wherein one or more additional cells are added to a cell group subsequent to issuance of the secure token to a token holder.
 9. The system of claim 1 wherein the one or more attributes associated with the directory are modified in terms of permitting or denying access to the directory by the plurality of applications.
 10. The system of claim 1 wherein the one or more attributes associated with a cell group are modified in terms of permitting or denying access to that cell group by the plurality of applications.
 11. The system of claim 1 wherein the one or more attributes associated with a cell are modified in terms of permitting or denying access to that cell by the plurality of applications.
 12. The system of claim 1 wherein the one or more attributes associated with a cell further control operations on contents of that cell by the plurality of applications.
 13. The system of claim 12 wherein the one or more attributes associated with the cell permit a first set of operations on the contents of that cell by a first application; wherein the one or more attributes associated with the cell permit a second set of operations on the contents of that cell by a second application; and wherein the first set of operations is different from the second set of operations.
 14. The system of claim 1 wherein the one or more attributes associated with the directory permit a first application to access the directory after a first access condition is satisfied; wherein the one or more attributes associated with the directory permit a second application to access the directory after a second access condition is satisfied; and wherein the first access condition is different from the second access condition.
 15. The system of claim 1 wherein the one or more attributes associated with the cell group permit a first application to access that cell group after a first access condition is satisfied; wherein the one or more attributes associated with the cell group permit a second application to access that cell group after a second access condition is satisfied; and wherein the first access condition is different from the second access condition.
 16. The system of claim 1 wherein the one or more attributes associated with the cell permit a first application to access that cell after a first access condition is satisfied; wherein the one or more attributes associated with the cell permit a second application to access that cell after a second access condition is satisfied; and wherein the first access condition is different from the second access condition.
 17. The system of claim 1 wherein the secure token is a smart card.
 18. The system of claim 17 wherein the smart card is an open platform smart card.
 19. The system of claim 17 wherein the smart card is a static or native smart card.
 20. A secure token comprising: a directory and one or more attributes associated with the directory, wherein the one or more attributes associated with the directory are used to control access to the directory by a plurality of applications, one or more cell groups under the directory, each cell group having one or more associated attributes, wherein the one or more attributes associated with a cell group are used to control access to that cell group by the plurality of applications, and one or more cells under each cell group, each cell having one or more associated attributes, wherein the one or more attributes associated with a cell are used to control access to that cell by the plurality of applications.
 21. The secure token of claim 20 wherein the one or more attributes associated with the directory permit access to the directory by one application and deny access to the directory to another application.
 22. The secure token of claim 20 wherein the one or more attributes associated with the cell group permit access to that cell group by one application and deny access to that cell group to another application.
 23. The secure token of claim 20 wherein the one or more attributes associated with the cell permit access to that cell by one application and deny access to that cell to another application.
 24. The secure token of claim 20 wherein one or more additional cell groups are added to the directory subsequent to issuance of the secure token to a token holder.
 25. The secure token of claim 20 wherein ownership of one of the one or more cell groups is determined subsequent to issuance of the secure token to a token holder.
 26. The secure token of claim 20 wherein ownership of one of the one or more cell groups is modified subsequent to issuance of the secure token to a token holder.
 27. The secure token of claim 20 wherein one or more additional cells are added to a cell group subsequent to issuance of the secure token to a token holder.
 28. The secure token of claim 20 wherein the one or more attributes associated with the directory are modified in terms of permitting or denying access to the directory by the plurality of applications.
 29. The secure token of claim 20 wherein the one or more attributes associated with a cell group are modified in terms of permitting or denying access to that cell group by the plurality of applications.
 30. The secure token of claim 20 wherein the one or more attributes associated with a cell are modified in terms of permitting or denying access to that cell by the plurality of applications.
 31. The secure token of claim 20 wherein the one or more attributes associated with a cell further control operations on contents of that cell by the plurality of applications.
 32. The secure token of claim 31 wherein the one or more attributes associated with the cell permit a first set of operations on the contents of that cell by a first application; wherein the one or more attributes associated with the cell permit a second set of operations on the contents of that cell by a second application; and wherein the first set of operations is different from the second set of operations.
 33. The secure token of claim 20 wherein the one or more attributes associated with the directory permit a first application to access the directory after a first access condition is satisfied; wherein the one or more attributes associated with the directory permit a second application to access the directory after a second access condition is satisfied; and wherein the first access condition is different from the second access condition.
 34. The secure token of claim 20 wherein the one or more attributes associated with the cell group permit a first application to access that cell group after a first access condition is satisfied; wherein the one or more attributes associated with the cell group permit a second application to access that cell group after a second access condition is satisfied; and wherein the first access condition is different from the second access condition.
 35. The secure token of claim 20 wherein the one or more attributes associated with the cell permit a first application to access that cell after a first access condition is satisfied; wherein the one or more attributes associated with the cell permit a second application to access that cell after a second access condition is satisfied; and wherein the first access condition is different from the second access condition.
 36. The secure token of claim 20 wherein the secure token is a smart card.
 37. The secure token of claim 36 wherein the smart card is an open platform smart card.
 38. The secure token of claim 36 wherein the smart card is a static or native smart card.
 39. A method for facilitating data management on a secure token, comprising: providing a directory and one or more attributes associated with the directory, wherein the one or more attributes associated with the directory are used to control access to the directory by a plurality of applications, providing one or more cell groups under the directory, each cell group having one or more associated attributes, wherein the one or more attributes associated with a cell group are used to control access to that cell group by the plurality of applications, and providing one or more cells under each cell group, each cell having one or more associated attributes, wherein the one or more attributes associated with a cell are used to control access to that cell by the plurality of applications.
 40. The method of claim 39 wherein the one or more attributes associated with the directory permit access to the directory by one application and deny access to the directory to another application.
 41. The method of claim 39 wherein the one or more attributes associated with the cell group permit access to that cell group by one application and deny access to that cell group to another application.
 42. The method of claim 39 wherein the one or more attributes associated with the cell permit access to that cell by one application and deny access to that cell to another application.
 43. The method of claim 39 further comprising: adding one or more additional cell groups to the directory subsequent to issuance of the secure token to a token holder.
 44. The method of claim 39 further comprising: determining ownership of one of the one or more cell groups subsequent to issuance of the secure token to a token holder.
 45. The method of claim 39 further comprising: modifying ownership of one of the one or more cell groups subsequent to issuance of the secure token to a token holder.
 46. The method of claim 39 further comprising: adding one or more additional cells to a cell group subsequent to issuance of the secure token to a token holder.
 47. The method of claim 39 further comprising: modifying the one or more attributes associated with the directory in terms of permitting or denying access to the directory by the plurality of applications.
 48. The method of claim 39 further comprising: modifying the one or more attributes associated with a cell group in terms of permitting or denying access to that cell group by the plurality of applications.
 49. The method of claim 39 further comprising: modifying the one or more attributes associated with a cell in terms of permitting or denying access to that cell by the plurality of applications.
 50. The method of claim 39 wherein the one or more attributes associated with a cell further control operations on contents of that cell by the plurality of applications.
 51. The method of claim 50 wherein the one or more attributes associated with the cell permit a first set of operations on the contents of that cell by a first application; wherein the one or more attributes associated with the cell permit a second set of operations on the contents of that cell by a second application; and wherein the first set of operations is different from the second set of operations.
 52. The method of claim 39 wherein the one or more attributes associated with the directory permit a first application to access the directory after a first access condition is satisfied; wherein the one or more attributes associated with the directory permit a second application to access the directory after a second access condition is satisfied; and wherein the first access condition is different from the second access condition.
 53. The method of claim 39 wherein the one or more attributes associated with the cell group permit a first application to access that cell group after a first access condition is satisfied; wherein the one or more attributes associated with the cell group permit a second application to access that cell group after a second access condition is satisfied; and wherein the first access condition is different from the second access condition.
 54. The method of claim 39 wherein the one or more attributes associated with the cell permit a first application to access that cell after a first access condition is satisfied; wherein the one or more attributes associated with the cell permit a second application to access that cell after a second access condition is satisfied; and wherein the first access condition is different from the second access condition.
 55. The method of claim 39 wherein the secure token is a smart card.
 56. The method of claim 55 wherein the smart card is an open platform smart card.
 57. The method of claim 55 wherein the smart card is a static or native smart card. 